Use new SBT Debian Repo before bintray is shutdown #7926
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We started seeing issues with building the TVM Docker images, and they stemmed from the SBT (Scala Build Tool) installation which was using bintray instead of a later SBT Debian URL. Thankfully bintray were just running some brown outs before they turn the service off on May 1st: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ So I took the Scala repo URL from here: https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html Which is the suggested SBT URL as they may change the backend again in future: sbt/sbt#6294
eed3si9n
reviewed
Apr 26, 2021
docker/install/ubuntu_install_sbt.sh
Outdated
| echo "deb https://dl.bintray.com/sbt/debian /" | tee -a /etc/apt/sources.list.d/sbt.list | ||
| echo "deb https://repo.scala-sbt.org/scalasbt/debian /" | tee -a /etc/apt/sources.list.d/sbt.list |
There was a problem hiding this comment.
Suggested change
| echo "deb https://dl.bintray.com/sbt/debian /" | tee -a /etc/apt/sources.list.d/sbt.list | |
| echo "deb https://repo.scala-sbt.org/scalasbt/debian /" | tee -a /etc/apt/sources.list.d/sbt.list | |
| echo "deb https://repo.scala-sbt.org/scalasbt/debian all main" | tee /etc/apt/sources.list.d/sbt.list | |
| echo "deb https://repo.scala-sbt.org/scalasbt/debian /" | tee /etc/apt/sources.list.d/sbt_old.list |
There was a problem hiding this comment.
Sorry I haven't had time to update the docs but the new Debian packages are now under all main.
There was a problem hiding this comment.
Not a problem, thanks for pointing it out 😸
|
I guess this is now ready to be merged? |
echuraev
pushed a commit
to echuraev/tvm
that referenced
this pull request
Apr 29, 2021
* Use new SBT Debian Repo before bintray is shutdown We started seeing issues with building the TVM Docker images, and they stemmed from the SBT (Scala Build Tool) installation which was using bintray instead of a later SBT Debian URL. Thankfully bintray were just running some brown outs before they turn the service off on May 1st: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ So I took the Scala repo URL from here: https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html Which is the suggested SBT URL as they may change the backend again in future: sbt/sbt#6294 * Future-proof sbt repo setup
umangyadav
pushed a commit
to umangyadav/tvm
that referenced
this pull request
May 5, 2021
* Use new SBT Debian Repo before bintray is shutdown We started seeing issues with building the TVM Docker images, and they stemmed from the SBT (Scala Build Tool) installation which was using bintray instead of a later SBT Debian URL. Thankfully bintray were just running some brown outs before they turn the service off on May 1st: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ So I took the Scala repo URL from here: https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html Which is the suggested SBT URL as they may change the backend again in future: sbt/sbt#6294 * Future-proof sbt repo setup
trevor-m
pushed a commit
to trevor-m/tvm
that referenced
this pull request
May 6, 2021
* Use new SBT Debian Repo before bintray is shutdown We started seeing issues with building the TVM Docker images, and they stemmed from the SBT (Scala Build Tool) installation which was using bintray instead of a later SBT Debian URL. Thankfully bintray were just running some brown outs before they turn the service off on May 1st: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ So I took the Scala repo URL from here: https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html Which is the suggested SBT URL as they may change the backend again in future: sbt/sbt#6294 * Future-proof sbt repo setup
trevor-m
pushed a commit
to trevor-m/tvm
that referenced
this pull request
May 6, 2021
* Use new SBT Debian Repo before bintray is shutdown We started seeing issues with building the TVM Docker images, and they stemmed from the SBT (Scala Build Tool) installation which was using bintray instead of a later SBT Debian URL. Thankfully bintray were just running some brown outs before they turn the service off on May 1st: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ So I took the Scala repo URL from here: https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html Which is the suggested SBT URL as they may change the backend again in future: sbt/sbt#6294 * Future-proof sbt repo setup
17 tasks
trevor-m
pushed a commit
to trevor-m/tvm
that referenced
this pull request
May 6, 2021
* Use new SBT Debian Repo before bintray is shutdown We started seeing issues with building the TVM Docker images, and they stemmed from the SBT (Scala Build Tool) installation which was using bintray instead of a later SBT Debian URL. Thankfully bintray were just running some brown outs before they turn the service off on May 1st: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ So I took the Scala repo URL from here: https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html Which is the suggested SBT URL as they may change the backend again in future: sbt/sbt#6294 * Future-proof sbt repo setup
trevor-m
pushed a commit
to neo-ai/tvm
that referenced
this pull request
May 11, 2021
* Use new SBT Debian Repo before bintray is shutdown We started seeing issues with building the TVM Docker images, and they stemmed from the SBT (Scala Build Tool) installation which was using bintray instead of a later SBT Debian URL. Thankfully bintray were just running some brown outs before they turn the service off on May 1st: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ So I took the Scala repo URL from here: https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html Which is the suggested SBT URL as they may change the backend again in future: sbt/sbt#6294 * Future-proof sbt repo setup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We started seeing issues with building the TVM Docker images, and they stemmed from the SBT (Scala Build Tool) installation which was using bintray instead of a later SBT Debian URL. Thankfully bintray were just running some brown outs before they turn the service off on May 1st:
https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
So I took the Scala repo URL from here:
https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html
Which is the suggested SBT URL as they may change the backend again in future:
sbt/sbt#6294
@leandron